System for communication with devices on a network to minimize power consumption

ABSTRACT

A system of controlling one or more building automation devices. The system may incorporate communicating over a first network with one or more network connected devices. An access point for the first network may be utilized to facilitate communication among the network connected devices. One or more of the network connected devices may be a low power device that has a first mode and a second mode. The low power device may expend less energy in one of the first mode and the second than in the other of the first mode and the second mode. The system may allow network devices connected to the first network to receive details about the low power device while the low power device is operating with the first mode and the second mode.

This application is a continuation of U.S. application Ser. No.15/557,782, which is a U.S. National Stage filing under 35 U.S.C. 371 ofInternational Application No. PCT/US2016/22218, filed Mar. 11, 2016,which claims the benefit of U.S. Provisional Application No. 62/132,437filed Mar. 12, 2015 and claims the benefit of U.S. ProvisionalApplication No. 62/138,853 filed Mar. 26, 2015. U.S. application Ser.No. 15/557,782, International Application No. PCT/US2016/22218, U.S.Provisional Application No. 62/132,437, and U.S. Provisional ApplicationNo. 62/138,853 are all hereby incorporated by reference in theirentirety.

BACKGROUND

The present disclosure pertains to communicating between networkconnected devices and particularly communicating with a low or reducedpower device connected to the network.

SUMMARY

The disclosure reveals systems for communicating over a network andbetween two or more network connected devices. In some cases, one ormore of the network connected devices may be a low power device that isconfigured to switch operations between a first mode (e.g., a low powermode) and a second mode (e.g., a higher power mode relative to the lowpower mode). The low power device may listen for communication signalsdirected at it when in the second mode, but not necessarily when in thefirst mode. In some cases, the system may incorporate a proxy deviceacting as a proxy for the low power device. The proxy device may receiveand identify communication signals related to the low power device andrespond to those communication signals with one or more details aboutthe low power device. The proxy may be a local proxy device (e.g., adevice connected directly to the first network or other device) and/or aremote proxy device (e.g., a remote server or other device connected tothe first network via a second network).

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a schematic diagram of an illustrative example of networkconnected devices;

FIG. 2 is a schematic diagram of a further illustrative example systemof network connected devices;

FIG. 3 is a schematic diagram of an illustrative example ofcommunication over a network;

FIG. 4 is a schematic diagram of an illustrative example ofcommunication over a network with a remote server;

FIG. 5 is a schematic diagram of a further illustrative example ofcommunication over a network with a remote server;

FIG. 6 is a schematic diagram of an illustrative example ofcommunication of multicast packets of data over a network;

FIG. 7 is a schematic diagram of a further illustrative example ofcommunication of multicast packets of data over a network;

FIG. 8 is a schematic flow diagram of illustrative examples ofcommunications over a network;

FIG. 9 is a schematic flow diagram of illustrative examples ofcommunications over a network with a low power device;

FIG. 10 is a schematic flow diagram of further illustrative examples ofcommunications over a network with a low power device;

FIG. 11 is a schematic flow diagram of further illustrative examples ofcommunications over a network with a low power device;

FIG. 12 is a schematic flow diagram of further illustrative examples ofcommunications over a network with a low power device;

FIG. 13 is a schematic flow diagram of illustrative examples ofcommunications over a network with a low power device via a proxy; and

FIG. 14 is a schematic flow diagram of illustrative examples ofcommunications over a network with a low power device via a proxy.

DESCRIPTION

The present system and approach may incorporate one or more processors,computers, controllers, user interfaces, wireless and/or wireconnections, and/or the like, in an implementation described and/orshown herein.

This description may provide one or more illustrative and specificexamples or ways of implementing the present system and approach. Theremay be numerous other examples or ways of implementing the system andapproach.

Standardized systems of configuration, communication, and/or control(e.g., Apple™ HomeKit or other systems via a Bonjour service or othermulticast Domain Name System (mDNS) service) may enable a user to havewireless and electronic control of one's home, household features,activities, appliances, and so forth. Such systems may provide aframework for communicating with and controlling connected accessoriesin a user's home or other area around a user.

A framework of a standardized system may specify a set of requirementsfor devices to facilitate communication between the devices over anetwork (e.g., an internet protocol (IP) network). These requirementsmay require devices (e.g., controllers and/or accessories capable ofbeing controlled by controllers) to respond to multicast and/or unicasttraffic originating from a device to allow the device to discover otherdevices and the other devices' services, along with allowing the deviceto pair with and access the services of the other devices. In somecases, this may result in a device having its transceiver turned on mostof the time to meet the specifications of the standardized system ofconfiguration, communication, and/or control.

A device (e.g., an accessory and/or a controller) may need to maintain along battery life. Maintaining a long battery life may be difficultwhile complying with a standardized system of configuration,communication, and/or control. In some cases, a device may utilize largerechargeable batteries, but such batteries may be expensive. Thepresently disclosed system may allow devices to maintain a long batterylife while complying with specifications of a standardized system ofconfiguration, communication, and/or control. In an example system,devices may be allowed to be in a sleep mode for a portion of anoperating time and an awake mode for a portion of an operating time ofthe device to facilitate complying with requirements of a standardizedsystem and requirements for battery life or a power stealing mechanism.

Standardized systems for configuration, communication, and/or control(e.g., HomeKit or other systems) may use a specified communicationprotocol (e.g., Bonjour protocol (service) or other service discoveryprotocols) for discovering new devices, services offered by new devices,resolving IP addresses of devices, and/or for other purposes.Additionally, or alternatively, the specified communication protocol maybe used for finding unique local IP addresses (e.g., link-localaddresses) and/or unique names for services and devices. In some cases(e.g., in the case of the Bonjour protocol), a specified communicationprotocol may achieve these functions by multicasting messages to awell-known multicast address and well-known port number (e.g., anaddress and/or port number of an access port (e.g., a router) or otherwell-known address and/or well-known port number).

While low power devices on Wi-Fi networks may make use of power-savemechanisms to sleep and still receive unicast data (e.g., data sent to asingle address and/or port, such as a request for a specific device, aresponse to a request by a device, and so on), devices utilizing powersave mechanisms may not necessarily be equipped to ensure delivery ofmulticast data (e.g., data sent to multiple addresses and/or ports, suchas a request for addresses and/or ports of devices connected to anetwork, a request for devices connected to the network having a similarname to the request device, and so on). An access point of a network(e.g., a router broadcasting the network or other access point)receiving unicast data from any source destined for a sleeping device(e.g., a device in a power-save mode) may hold the data for the sleepingdevice until the device wakes up and polls for the data.

However, no such provisions appear available for multicast data. Anaccess point for a network may have certain periodic times when it willtransmit all multicast data received during a period. The periods may bedependent on the access point settings, specifications of standardizedsystems of configuration, communication, and/or control, and/orrequirements of a communication protocol. Example periods for sendingand/or transmitting multicast data may incorporate, but are not limitedto, 50 milliseconds (ms), 100 ms, 200 ms, 300 ms, 400 ms, 500 ms, 1second, over 1 second or other time periods. Hence, if a period is 300ms, a sleeping device that may be sleeping for more than 300 ms maycompletely miss a reception of the multicast data. This apparentshortcoming in the reception of multicast data may make it difficult tocommunicate with low-power sleeping Wi-Fi devices on a network wheremulticast data are transmitted at set time periods.

The system disclosed may provide several ways of solving such issues andallow low power sleeping Wi-Fi devices to take part in specified systemsof configuration, communication and/or control. In one example, thesystem may solve the issue with one or more of several approaches bywhich multicast data traffic intended for a low power sleeping device iseither received or acted upon appropriately by the sleeping device orother device in communication with the sleeping device.

In a first set of approaches, functionality of a low power device may bealtered to ensure probes, queries, and resolutions of other devicesusing a communication protocol and/or a standardized system ofconfiguration, communication and/or control may be responded to. Acommunication protocol (e.g., a Bonjour protocol) may be a multicastmechanism and hence any service discovered by one device canautomatically be also discovered and cached by all other devices in themulticast group. Some approaches that one may use in the first set ofapproaches may incorporate a gratuitous periodic query response approachand a periodic query request and response on wake up approach.

With gratuitous periodic query response approaches, a low power devicemay provide other devices advance notification of its details. That is,a low power device may update cache (e.g., communication protocol (e.g.,Bonjour protocol)/MDNS cache or other cache) of other devices beforethose other devices ask for the update and/or before the low powerdevice knows the other devices asked for the update. In one example, theupdates may be communication protocol publication and discovery packetsoriginating from the low power device after every wakeup from sleep or adifferent set period. Thus, this may help a control device or otherdevice to discover the sleeping device and/or update the sleepingdevice's state.

In the gratuitous response approach, a low power device may registerwith an MDNS responder (e.g., access point) and announce its servicesautomatically for a first time and in order to implement periodic sleepand wakeup cycles; the low power device may initiate an automatic updateof the MDNS cache in control devices by sending an unsolicited query anda response to the query from the low power device on every wakeup usinglow level “update service” APIs or other mechanisms. This may ensurethat the gratuitous response can help with a service discovery forcontrol devices and other devices entering the network, name and IPaddress collision resolution on a standardized system configuration,communication, and control (e.g., HomeKit) and/or a communicationprotocol (e.g., Bonjour) for devices in the network, and provide aresolution of the SRV, TXT and other record types by control devices.This behavior on the low power device may be continued in both pairedand unpaired states of the communication protocol. This approach mayalso involve optional gratuitous ARP queries to resolve an ARP requestfrom a control device (e.g., phone, laptop, tablet computer, personalcomputer, other controller, and so forth).

The second approach (Periodic Query request and response on wake up) maybe a variation on the first approach. In addition to the queryresponses, actual query requests may be sent out from low power deviceson the network upon every wakeup from sleep. The low power device maysend out an MDNS query for its matching service type and may alsoinitiate a response to this query with its services before entering intoa sleep mode. This approach may follow the standard MDNS queryrequest/response behavior instead of implementing the unsolicited queryresponse behavior mentioned above. This may ensure communicationprotocol conformance (e.g., some communication protocols may not allowresponse without a query requesting a response). Such behavior on thelow power device may be continued in both paired and unpaired states ofthe communication protocol (e.g., HomeKit accessory protocol). Thisapproach may also involve optional gratuitous ARP queries to resolve anARP request from a control device (e.g., phone, laptop, tablet computer,personal computer, and so on).

Additional approaches may be aimed at changing the functionality of bothcontrollers (e.g., phones, laptop computers, tablet computers, and soforth) and low power devices (e.g., battery operated computing devices,computing devices with power stealing mechanisms, and/or other low powerdevices, which may incorporate, but are not limited to, thermostats,building automation sensors, HVAC controllers, cameras, video cameras,and/or other building automation devices). In these approaches, anoperation of the control devices (e.g., communication protocol compliantdevices) may change in addition to changing an operation of the lowpower devices. These approaches may incorporate cached information abouta service (e.g., a service of a low power device or other service) thatutilizes a local proxy for a lower power device, and/or utilizes a widearea proxy for a low power device.

In a cached information about a service approach, a control device orother device connected to a network may be asked and/or required tocache and remember details (e.g., information about an IP address, aport number, a device name, and/or a service name) of low power devicesover long periods of time (e.g., periods of time including disconnectingand/or re-connecting to the network). Such details of the lower powerdevices may be cached against a network ID and/or password hash of thenetwork, and thus when the controller or other device goes out and comesback into the network, the controller or other device does notnecessarily have to re-discover the services of the low power device bymulticasting queries to the network. In some cases, the control devicemay send out unicast queries with update requests to low power deviceshaving details stored in the cache of the control devices.

In the cached information about a service approach, the low power devicemay implement a read only service characteristic to indicate that it isa low power device. The low power device may initially register with anaccess point (e.g., an MDNS responder) and announce its servicesautomatically for the first time and follow one or more of theGratuitous response approach and the Periodic Query request and responseapproach proposed to periodically report services. But once the lowpower device gets paired or successfully performs a pair verify with thecontrol device, the control device may keep a cache of the services ofthe low power device and check for the service characteristic updatesusing unicast query requests only. Any new control device added to thenetwork may learn about this service characteristic of the low powerdevice and initiate a periodic unicast request for low power devicestate. The low power device, upon pair removal, may go back to theinitial state and follow any of the first two approaches to advertiseits services for the controllers on the local network until the lowpower device performs a pairing or successful pair verify with thecontrol device. This approach may implement gratuitous ARP queries toresolve an ARP request from a control device (e.g., phone, laptop,tablet computer, personal computer, and so on) and also to help detectIP conflicts or change in IP addresses and assist in updating the ARPtables of the control devices on the network.

This approach may make the accessory device less chatty compared to thefirst two approaches, reducing a number of transmissions and improvingbattery life. A periodic return to the chatty behavior as described inapproach one may be needed.

In the proxy-based (e.g., local proxy and/or wide area proxy)approaches, a third device may be used as a proxy for one or more lowpower sleeping devices. In one example, the proxy device may reply tomulticast queries on behalf of the low power devices for which it is aproxy. The low power device in turn may keep the multicast data at theproxy up-to-date with its service details by updating the informationperiodically and upon change.

The low power device and the proxy may communicate over any network,which may or may not be the network to which other network connecteddevices are connected. In one example, the low power device and theproxy may communicate over Bluetooth™, Bluetooth™ Low Energy (BLE),near-field communication (NFC), Wi-Fi, and/or one or more otherproprietary or non-proprietary communication protocols.

If the proxy is in the same local network as the low power devices, itmay be considered a local area proxy. If the proxy is a server on thecloud with a well-known IP address and port number, the proxy may be awide area proxy.

In the local multicast proxy approach, the low power device mayinitially work in a chatty manner when it first joins the network.However, when a proxy device is discovered by the low power device, thelow power device may register for the proxy service with the proxydevice. From that point, virtually all multicast queries for specificservices in the low power device or generic “any” queries may beanswered by the proxy device on behalf of the low power device. The lowpower device may have the responsibility to keep the proxy deviceup-to-date with the current conditions and state of the low powerdevice.

In the wide area multicast proxy approach, the low power device mayinitially register for the proxy service with a proxy capable cloudserver having a well-known IP address (e.g., similar to wide areaBonjour). Control devices may send queries to the cloud server inaddition to multicasting on the local network. The cloud server maymatch the ISP provided IP address where the query is coming from withthe ISP provided IP address used to register the service by the lowpower device and return all the relevant information in a query responseto the controller. This approach may be useful if there is an internetconnection. If there is not internet connection, the low power devicemay have to revert back to chatty behavior.

A further approach may depend on the power consumption models for thelow power device. In this approach, a control device may ensure thatvirtually all queries are repeated often in a set period. The period maybe equal to the sleep interval of the low power device. Thus, it may beensured that each query is heard by the low power device.

In operation, a device may communicate over Wi-Fi/Ethernet or othercommunication system (e.g., Bluetooth™, Bluetooth™ Low Energy, and soforth). During normal operation, such a device may implement protocolspecific standard sleep mechanisms. A Wi-Fi supported device mayconfigure a listen interval duration and may use any standard IEEE powersave mechanisms (Power save poll, power save without poll, WMM powersave, and so on) to enter into a sleep mode. The device may then stayawake for a minimum timeout interval to perform its own TCP/IPtransactions and respond to other possible unicast queries originatedfrom controllers before entering to sleep again.

Turning to the figures, FIG. 1 depicts a network 10 with a networkconnected device (e.g., a network device 12) in communication with anaccess point 14. The network 10 may be a local area network (LAN) and/orother network type (e.g., a wide area network (WAN) or a network thatmay be part of a WAN). The network device 12 may be in communicationwith the access point 14 over Wi-Fi or Ethernet. Alternatively or inaddition, the network device 12 may be in communication with the accesspoint 14 over one or more other communication systems including, but notlimited to, ZIGBEE, Bluetooth™, Bluetooth™ Low Energy, Near FieldCommunication (NFC), radio frequency, and so on.

The network device 12 may incorporate a memory 16, a controller 18, aninput/output (I/O) port 20, power source 22, and/or other components,where the components of the network device 12 may communicate with oneanother. A network device 12 may be any type of device configured toconnect to the network. In one example, the network device 12 may be abuilding automation device (e.g., a thermostat, a camera, a videocamera, a carbon monoxide detector, a smoke detector, one or moresensors, a light bulb, an HVAC controller, and so forth) and/or adifferent device.

The access point 14 may incorporate a memory 24, a controller 26, an I/Oport 28, and a power source 30, where the components of the access point14 may communicate with one another. The access point 14 may be any typeof device configured to facilitate providing access to the network 10.In one example, the access point 14 may be a router and/or other accesspoint.

FIG. 2 depicts a network (e.g., network 10) that may incorporate one ormore devices connected to the access point 14. In one example, theaccess point 14 may be in communication with one or more network devices12 (e.g., network device 1 12 a, network device 2 12 b, . . . networkdevice N 12 c), one or more servers 32, and one or more control devices34. The network devices 12 in communication with the access point 14 maycommunicate with one another and/or other devices separate from and/orthrough the access point 14.

The one or more servers 32 may be located local to the access point 14or remote from the access point 14 and may be connected to the accesspoint 14 over a LAN or a WAN. Although not shown, the server may be acomputing device having memory, a controller, an I/O port, a powersource, and/or other components, where components of the server 32 maycommunicate with one another. Illustratively, the server may communicatewith one or more access points 14 at one or more different or similargeographical locations.

In one example, the server 32 may be a server of a manufacturer of anetwork device 12. In such an example, the manufacturer may be amanufacturer of a building automation device and the server 32 mayincorporate account information for an owner of the building automationdevice and/or device information for the specific building automationdevice (e.g., media access control (MAC) address, IP address, portnumber, device name on a network, and so on).

The control device 34 may be in communication with the access point 14over Wi-Fi or Ethernet. Alternatively or in addition, the control device34 may be in communication with the access point 14 over one or moreother communication systems including, but not limited to, ZIGBEE,Bluetooth™, Bluetooth™ Low Energy, Near Field Communication (NFC), radiofrequency, and so on.

The control device 34 may incorporate a memory 36, a controller 38, aninput/output (I/O) port 40, a power source 42, and/or one or more othercomponents, where the components of the control device 34 maycommunicate with one another. A control device 34 may be any type ofdevice configured to connect to the network. In one example, the controldevice 34 may be a smart phone, a tablet computer, a personal computer,a laptop and/or a different device. Although only a single controldevice 34 is depicted connected to the access point 14, one or moreadditional and/or alternative control devices 34 may be in communicationwith the access point 14, each other, and/or other devices separate fromand/or through the access point 14.

As discussed above, the computing devices discussed herein (e.g.,network device 12, access point 14, server 32, control device 34, and soforth) may be configured to connect to and communicate with one anotherover one or more networks. Such computing devices may incorporate amemory, one or more controllers, one or more I/O ports, and one or morepower sources. Additionally or alternatively, the computing devicesdisclosed herein may incorporate one or more other components.

The network 10 may incorporate one or more networks and may incorporateone or more types of networks. Illustratively, the network 10 mayincorporate a local area network (LAN), a wide area network (WAN),and/or one or more other networks connecting two or more computingdevices. Although numerous networks may be disclosed as connecting twoor more computing devices, these networks 10 may be a single network orseveral networks.

The controllers of the computing devices may incorporate one or moreprocessors. The controllers may be or incorporate one or moremicro-controllers and/or one or more micro-processors. The controllersand/or processors thereof may be in communication with memory of thecomputing devices or other memory and may be configured to executeexecutable instructions stored on the memory and/or store and use datasaved on the memory. In one example, the memory of the computing devicemay incorporate one or more control system algorithms and/or otheralgorithms and the controller may execute instructions (e.g., softwarecode or other instructions) related to the algorithms in the memory.

The memory of the computing devices may incorporate one or more piecesof memory, one or more types of memory, and/or any combination of typesof memory. For example, the memory may be volatile memory, non-volatilememory (e.g., FLASH or other non-volatile memory), random access memory(RAM), read-only memory (ROM), removable memory (e.g., a USB drive orother removable drive) and/or one or more other types of memory. In somecases, the memory may be configured to store data and/or instructionsfor execution by the controllers (e.g., one or more processors of thecontrollers) of the computing devices.

The I/O ports of the computing devices may send and/or receiveinformation and/or control signals to and/or from other computingdevices on the network 10. The I/O ports may be any type ofcommunication ports and may facilitate wired and/or wirelesscommunication with the network 10 and the computing devices on thenetwork. For example, the I/O ports may facilitate communication withthe network 10 and/or other devices (e.g., network devices 12, accesspoints 14, servers 32, control devices 34, and/or other devices) throughany connection including, but not limited to, radio communication,Ethernet, cellular communication, ZigBee, REDLINK™ Bluetooth, BluetoothLow Energy (BLE), Wi-Fi, IrDA, dedicated short range communication(DSRC), EnOcean, Near Field Communication (NFC), and/or any othersuitable common (non-proprietary) or proprietary wired or wirelessprotocol.

FIGS. 3-7 illustrate various approaches for communication amongcomputing devices connected to the network 10. FIG. 3 depicts anapproach for a network device 12 (e.g., a low power device connected tothe network 10) utilizing a power save mechanism to communicate over anetwork. Illustratively, a low power device may be a network device 12that is utilizing a power save mode/mechanism (e.g., where thecontroller 18 of the network device 12 may place the device in a sleepmode or an awake mode according to a schedule to save power over time).In some cases, a power save mode may be selected by a user.Alternatively, or in addition, the network device 12 may automaticallyenter a power save mode when operating with a power source of a battery,a power stealing mechanism, or other non-line power, power source.

As shown in FIG. 3, an access point 14 for a network (e.g., network 10)may be configured to send beacons 58 to one or more network devices 12or other devices connected to the network. The beacons 58 may bebroadcast from the access point 14 at regular intervals, as discussedabove with respect to access point 14.

In one example, the controller 26 of the access point 14 may beconfigured to initiate the beacons 58. The beacons 58 from the accesspoint 14 may be broadcast from the I/O port 28.

The beacons 58 may provide unicast and/or multicast packets of data(e.g., indications (e.g., indications that messages may be held at theaccess point 14), information, requests, commands, and/or other data) todevices connected to the network. Multicast and/or broadcast packets ofdata may be data packets directed to at least two devices connected tothe network, whereas unicast data packets may be data packets directedto a specific device connected to the network.

In some cases, the beacons 58 may incorporate address and/or nameinformation for one or more devices connected to the network to whichthe data in the beacon 58 may be sent. Alternatively or in addition,beacon 58 may be sent to all devices connected to a network without aindicating in the beacon 58 a specific address for the data.

The network devices 12 and/or other devices connected to the network maybe configured to listen via the I/O port 20, 40 for a beacon 58 directedat that network device 12. In some cases, the network device 12 maylisten 56 for a beacon 58 periodically at a listen interval. In FIG. 3,an example listen interval is three (3) beacons, such that the networkdevice 12 may listen 56 for a beacon 58 at three times a rate at whichthe beacons 58 may be broadcast (e.g., the network device 12 may listen56 for every third beacon 58).

A listen interval for a network device 12 may be set by the networkdevice 12 or a manufacturer of the network device 12. Alternatively orin addition, a user of the network device 12 may set the listeninterval. In one example, when a beacon 58 is broadcast every 100 ms, anexample listen interval might be one second (every ten beacons), twoseconds (every twenty beacons 58), four seconds (every forty beacons),and so forth.

FIG. 4 depicts an approach for a network device 12 in a power savingmode (e.g., a low power device) to receive data through an access point14 (e.g., the network device asks for weather forecast data, where thenetwork device 12 may be a thermostat or other building automationdevice). At arrow 60, the network device 12 may send a request for data,as initiated by the controller 18 and broadcast via I/O port 20, to theaccess point 14 and at arrow 62, the access point 14 may direct the datarequest from the network device 12 to another device connected to thenetwork or a server 32 connected to the access point 14. In some cases,devices may be connected to the access point 14 over a first network(e.g., a LAN), and the server 32 may be connected to the access point 14over a second network (e.g., a WAN), but this is not necessarilyrequired. After receiving the data request, the server 32 may send therequested data back to the access point 14 at arrow 64. Then, at arrows66 the access point 14 may broadcast beacons (e.g., beacons with atraffic indication map (TIM)) that indicate the access point 14 isholding data for the network device 12.

As the data received from the server 32 may be directed at a singlenetwork device 12 (e.g., as it was requested by a single network device12), the data may be a unicast packet of data and the access point 14may able to keep the data until the network device 12 is ready toreceive the data. At arrow 68 from the access point 14, when the networkdevice 12 wakes up and a listen interval lines up with a beacon from theaccess point 14 and sees a beacon with a TIM for the network device 12,the network device 12 may now know that the access point 14 is holdingdata to be delivered to it. At arrow 70, the network device 12 maybroadcast to the access point 14 that it would like its data now. Thenat arrow 72, the access point 14 may send the data to the network device12. After the network device 12 has received its data, the networkdevice 12 may go back to sleep and listen 56 for communication on thenetwork only every listen interval or other interval.

FIG. 5 depicts another approach for a network device 12 in a powersaving mode (e.g., a low power device) to receive data through an accesspoint 14 (e.g., the network device asks for weather forecast data, wherethe network device 12 may be a thermostat or other building automationdevice). The network device 12 may request data via the access point 14and the access point 14 may receive the requested data in a similarmanner to as is shown in FIG. 4. Then, at arrows 66 the access point 14may broadcast beacons (e.g., beacons with a traffic indication map(TIM)) that indicate the access point 14 is holding data for the networkdevice 12.

As was the case with respect to the approach depicted in FIG. 4, thedata received from the server 32 may be directed at a single networkdevice 12 and may be a unicast packet of data that the access point 14may be able to keep until the network device 12 is ready to receive thedata. At arrow 68 from the access point 14, a listen interval lines upwith a beacon from the access point 14 and the network device 12 may nowknow that the access point 14 is holding data to be delivered to thenetwork device 12. At arrow 70, the network device 12 may broadcast tothe access point 14 that it is now awake and ready to receive the databeing held by the access point 14. At arrow 72, the access point 14 maysend (e.g., broadcast) the data to the network device 12. After thenetwork device 12 has received its data, the network device 12 at arrow74 may tell the access point 14 that it is going back to sleep and notto send any more data. The network device may then go back to sleep andlisten 56 for communication on the network only every listen interval orother interval.

In some cases, a beacon 58 may incorporate a distributed trafficindication map (DTIM). As shown in FIG. 6, DTIM beacons from the accesspoint 14 may be represented by dashed arrows 76 and elongated arrow 78.The DTIM beacons in FIG. 6 are every other beacon and thus, have aperiod of 2 beacons. However, other periods are possible.

A DTIM may indicate an access point 14 has multicast and/or broadcastdata packets for immediate or nearly immediate delivery by the accesspoint 14 to devices connected to the network. A DTIM period may be aninterval between beacons 58 with a DTIM.

The DTIM period of an access point 14 may be set by the access point 14or a manufacturer of the access point 14 and/or by a user of the accesspoint 14. A DTIM period may be set to 1 beacon, 2 beacons, 3 beacons, 5beacons, 10 beacons or other number of beacons, as desired.

In FIG. 6, the DTIM beacon represented by arrow 78 may line up with whenthe network device 12 (e.g., a thermostat) is listening for a beacon. Asa result, the network device 12 may determine it will stay awake toensure it receives the multicast packet of data broadcast from theaccess point, as represented by arrow 80. After receiving the multicastpacket of data from the access point 14, the network device 12 may goback to sleep and resume listening for beacons at regular listeningintervals or other intervals.

FIG. 7 depicts an approach similar to that of FIG. 6, but where thenetwork device 12 may miss a multicast packet of data that is broadcastby the access point 14. However, in addition to the network device 12being in communication with the access point 14 over the network, acontrol device 34 (e.g., a network device 12), a network device N 12 c,and a new network device 12 d (e.g., a new network device 12 d may be anetwork device 12 that recently connected to the network) may be incommunication with the access point 14 over the network. As with FIG. 6,the DTIM beacons represented by arrows 76 may have a period of twobeacons, but this is not necessarily required.

As can be seen in FIG. 7, when the network device 12 is awake andlistening for beacons 58 from the access point 14 as represented byarrows 56, it may not always line up with a DTIM beacon represented byarrows 76. As a result, the network device 12 may be unaware that theaccess point 14 may have received a multicast packet of data to bedistributed immediately or nearly immediately. Because the networkdevice 12 may not know that the access point 14 has a multicast packetof data to be broadcast, the network device 12 may go to sleep and missthe broadcast of the multicast packet of data as represented by arrow82.

FIG. 7 illustrates the multicast packet of a data reception issue. Thatis, low power devices may need to sleep or have a sleep mode (e.g., haveperiods of time when the device is not listening/looking for data), butwhen the low power devices are asleep, the low power devices may missmulticast packets of data that are broadcast. To receive all multicastpackets of data, a network device 12 (e.g., a low power device) may needto listen to all DTIM beacons broadcast by the access point 14. However,listening to all DTIM beacons may be power intensive, especially if aDTIM period is small (e.g., 100 ms, 200 ms, and so on).

FIGS. 8-14 depict interactions between devices on a network. As shown inFIGS. 8-14, a control device 34, a new network device 12 d, and anetwork device N 12 c may communicate over a network (e.g., network 10via an access point 14, where an access point 14 has been omitted fromFIGS. 8-14 for clarity purposes). As shown in FIGS. 8-11, 13, and 14,three example instances of interactions between the control device 34, anew network device 12 d, and network device N 12 c are depicted: nameconflict resolution on the network; service discovery of devices on thenetwork; and address and other detail resolution on the network. FIGS.8-14 depict query arrows 44 and response arrows 46, where the flow of aconversation between devices may be followed by following the queryarrows 44 and response arrows 46 over time (e.g., from top to bottom).

Broadcast responses, as represented by arrows 46, may incorporate one ormore details about the network device 12 from which the arrowsoriginate. The broadcast responses may incorporate IP addressinformation, device name information, service name information, SRVrecords, PTR records, TXT records, and/or other information and/or datafrom the network device 12.

FIG. 8 depicts interactions between the devices on the network wherenetwork device N 12 c may always be listening for beacons from an accesspoint (e.g., the device N 12 c may be connected to line power or anyother sustained power supply as a power source). With a Name Conflictresolution procedure, a new network device 12 d may enter a network(e.g., network 10) and inquire over the network whether any other deviceconnected to the network has a name that the new network device 12 d ischoosing for itself. In one example, a new network device 12 d may bootup and select a name. Then, the new network device 12 d, as initiated bya controller 18, may send or broadcast via the I/O port 20 a multicastquery at arrow 44 asking whether any other device on the network has aname that is the same as the selected name. Network device N 12 c, whichmay be in an awake mode, may receive this query and if the device hasthe same name as the name selected by the new network device 12 d (e.g.,both network devices 12 may be a same type of thermostat or otherbuilding automation device), the network device N 12 c may respond, asinitiated by the controller 18, at arrow 46 via the I/O port 20indicating it has the same name as the selected name. As a result ofreceiving the response from the network device N 12 c, the new networkdevice 12 d may select another name and send out a further multicastquery at arrow 44 asking whether any network device 12 on the networkhas the newly selected name.

With a service discovery procedure as seen in FIG. 8, a control device34 may enter a network having the new network device 12 d and thenetwork device N 12 c, among optionally other network devices 12. Thecontrol device 34 may send out a multicast query at arrows 44 to the newnetwork device 12 d and the network device N 12 c asking what servicesare offered by the network devices 12 connected to the network. Then,the new network device 12 d and the network device N 12 c being in anawake mode may receive the multicast query and respond at arrows 46 tothe query with an indication of the services offered by the specificnetwork device 12.

With an address and other detail resolution as seen in FIG. 8, a controldevice 34 may enter a network having the new network device 12 d and thenetwork device N 12 c, among optionally other network devices 12. Thecontrol device 34 may send out a multicast query at arrows 44 to the newnetwork device 12 d and the network device N 12 c asking for addressand/or name details from the network devices 12 connected to thenetwork. Then, the new network device 12 d and the network device N 12 cbeing in an awake mode may receive the multicast query and respond atarrows 46 to the query with an indication of the details requested inthe query.

FIG. 9 depicts the problem referred to above with respect to FIG. 7 andlow power network devices 12 not receiving all multicast packets of datathat are broadcast from an access point 14. In FIG. 9, the networkdevice N 12 c may be a low power network device that enters a sleep mode(e.g., represented by boxes 54) to save power. Although the boxes 54 maybe spaced at different intervals and/or have different sizes, the sleepand listen intervals may be consistent (e.g., substantially always thesame) or vary over time.

As seen in FIG. 9 with respect to the service discovery procedure, amulticast query at arrows 44 may happen to reach the low power networkdevice N 12 c when the device is in an awake mode and the low powernetwork device N 12 c may respond at arrow 46, but it may not always bethe case that network device N 12 c will receive a multicast query whenit is in an awake mode. For example, as with the name conflictresolution period and the address and other detail resolution procedure,the multicast query as represented by arrows 44 may reach the low powernetwork device N 12 d while the low power network device N 12 d is in asleep mode and is not listening for a beacon. As a result, the networkdevice 12 (e.g., new network device 12 d or control device 34) makingthe query may not necessarily receive all of the information it needs,as represented by dash-dot arrows 44 and 46.

FIGS. 10-14 illustrate various approach to a solution to the issuesillustrated in FIGS. 7 and 9 and discussed above. In each approachillustrated, the network device N 12 c may be a low power network device12 with a controller configured to place the low power network device 12into a first mode (e.g., a sleep mode where it may not be listening forbeacons and/or multicast packets of data) and a second mode (e.g., anawake mode where it may be listening for beacons and/or multicastpackets of data). The various approaches may be used in combination withone another and/or individually.

FIG. 10 illustrates a gratuitous response approach. In the gratuitousresponse approach, the low power network device N may automaticallybroadcast and/or send a response at arrows 46 extending from the networkdevice N 12 c to the access point (not shown) and all network devices 12on the network (e.g., control device 34, new network device 12 d and/orother network devices 12) when it exits a sleep mode 54 and/or enters anawake mode without first being prompted by a request from anothernetwork device 12 received via the access point. The automatic responsesmay be broadcast from the low power network device N 12 c via the I/Oport 20 upon exiting the sleep mode and/or entering the awake mode, orwithin a set period of time (e.g., one second, two seconds, threeseconds, five seconds, or other period of time) of doing so. Theautomatic responses from the low power network device N 12 c mayincorporate details of the network device N 12 c (e.g., device name, theservices it renders (e.g., its functionality), its address, and so on),which may incorporate SRV records, PTR records, TXT records, and/orother records.

In addition to or instead of automatically sending a response when thelow power network device N 12 c exits a sleep mode or enters an awakemode, the low power network device N 12 c may send out its details atregular periodic intervals (e.g., after a period of time since the lastbroadcast of its details). In one example, the low power network deviceN 12 c may be configured to send out its details once every second, onceevery two seconds, once every three seconds, once every five seconds,once every ten seconds, once every twenty seconds, and/or at a differenttime period, which may or may not coincide with waking up from a sleepmode.

With the gratuitous response approach, the network device N 12 c may notneed to know if another network device 12 is requesting information andor sending a multicast query. As a result, all network devices 12 may beregularly updated with the details for the low power network devices N12 c and the network devices 12 may not be missing details for variouslow power network devices 12 on the network.

FIG. 11 illustrates a gratuitous query request and query responseapproach. In the gratuitous query request and response approach, the lowpower network device N 12 c may automatically broadcast and/or send viaan I/O port 20 a query request at arrows 44 to the access point (notshown) and all of the network devices 12 on the network. The low powernetwork device N 12 c may receive via the I/O port 20 and from theaccess point, the query request it sent and then, broadcast on aresponse to the query request at arrows 46 from the network device N 12c via the I/O port 20 to the access point (not shown) and all networkdevices 12 on the network (e.g., control device 34, new network device12 d and/or other network devices 12). The controller 18 of the lowpower network device N 12 c may initiate this procedure when it exits asleep mode 54 and/or enters an awake mode without first being promptedby a query request from another network device 12. The automatic queriesand responses to the requests may be broadcast from the low powernetwork device N 12 c via the I/O port 20 upon exiting the sleep modeand/or entering the awake mode, or within a set period of time (e.g.,one second, two seconds, three seconds, five seconds, or other period oftime) of doing so. The automatic query and responses from the low powernetwork device N 12 c may incorporate details of the network device N 12c (e.g., device name, the services it renders (e.g., its functionality),its address, and so forth), which may incorporate SRV records, PTRrecords, TXT records, and/or other records.

In addition to or instead of automatically sending a query and aresponse when the low power network device N 12 c exits a sleep mode orenters an awake mode, the low power network device N 12 c may broadcastand/or send out a query and its response with device specific details atregular periodic intervals (e.g., after a period of time since the lastbroadcast of its details). In one example, the low power network deviceN 12 c may broadcast a query request and then respond to its own queryrequest by broadcasting and/or sending its details, where the queryrequest may be initiated by the controller 18 thereof at intervals ofonce every second, once every two seconds, once every three seconds,once every five seconds, once every ten seconds, once every twentyseconds, and/or at a different time period, which may or may notcoincide with waking up from a sleep mode.

With the gratuitous query request and response approach, the low powernetwork device N 12 c may not need to know if another network device 12is requesting information and or sending a multicast query. As a result,all network devices 12 may be regularly updated with the details for thelow power network devices N 12 c and the network devices 12 may notnecessarily be missing details for various low power network devices 12on the network.

FIG. 12 illustrates a cached information about a service/deviceapproach. In the cached information about a service/device approach, acontrol device 34 or other network device 12 on a network may broadcastand/or send a query request as indicated at arrows 44 via an I/O port toan access point (not shown) and therethrough to virtually all of thenetwork devices 12 on the network (e.g., the new network device 12 d andthe network device N 12 c, as shown in FIG. 12). At arrows 46, each ofthe network devices 12 that receive the query request (e.g., the newnetwork device 12 d and the network device N 12 c) may broadcast and/orsend a response at arrows 46 via respective I/O ports 20 to the controldevice 34. The responses may incorporate one or more details about therespective network device 12 (e.g., device names, services names, IPaddresses, port numbers, and so on). After the control device 34 orother device receives responses from the network devices 12 on thenetwork, the control device may store the network device 12 information(e.g., details) in its memory 36 (e.g., cache) and tie the networkdevice information to details about the network (e.g., login credentialsfor network 10, address information for network 10, and so forth), atbox 90, and connect to the network via box 92.

If or when the control device 34 disconnects from the network andreconnects at a later time, the control device 34 may look for thedevices and/or services it has associated with the network in its memory36, as seen at box 94. In some cases, the control device 34 may thenbroadcast unicast data packets to the access point (not shown) fornetwork devices 12 stored in its memory 36, where the unicast datapackets may request updated details from the specific network device 12to which it is broadcast and/or sent.

FIG. 13 illustrates a local area sleep/multicast proxy approach. In thelocal area sleep/multicast proxy approach, a local proxy device 48 maybe utilized. The local proxy device 48 may be a computing device (e.g.,a network device 12) having a memory, a controller, an I/O port, and apower source, among other components and similar to as discussed abovewith respect to other computing devices. The local proxy device 48 maybe capable of connecting to the network via its I/O port andspecifically configured to act as a proxy for the low power networkdevice N 12 c, which may be configured to put itself into a sleep modeand/or an awake mode to save power during operation. The power source ofthe local proxy device 48 may be line power or other source of power.Additionally, the local proxy device 48 may always or substantiallyalways be in an awake mode listening for beacons directed at one or morenetwork device for which it is acting as a proxy.

Once the local proxy device 48 and the low power network device N 12 care connected to the network, the local proxy device 48 and the lowpower network device N 12 c may identify each other and beginbroadcasting and/or sending information to each other. The local proxydevice 48 and the low power network devices N 12 c may communicatebetween one another in any manner to allow a low power network device N12 c to provide the local proxy device 48 its updated details and/or toallow the local proxy device 48 to provide commands (e.g., from acontrol device 34) and/or the information to the low power networkdevice N 12 c. In one example, the local proxy device 48 may sendunicast data packets to the low power network device N 12 c to requestupdated information and/or send commands/information. Alternatively, orin addition, the low power network devices N 12 c may use periodic stateinformation updates to provide the local proxy device 48 with itsupdated information and/or to request information. The periodic stateinformation updates may be provided without a request from the localproxy device 48.

The local proxy device 48 and the low power network device N 12 c maycommunicate over any communication protocol. In one example, the localproxy device 48 and the low power network device N 12 c may communicatethrough any connection including, but not limited to, radiocommunication, Ethernet, cellular communication, ZigBee, REDLINK™,Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, IrDA, dedicated shortrange communication (DSRC), EnOcean, Near Field Communication (NFC),and/or any other suitable common (non-proprietary) or proprietary wiredor wireless protocol.

In the local area sleep/multicast proxy approach, the low power networkdevice N 12 c may provide its details to the local proxy device 48, asrepresented by arrow 50, and the local proxy device 48 may store thereceived details in its memory (e.g., cache). Thereafter, an accesspoint may broadcast multicast packets of data (e.g., from other networkdevices 12 on the network, such as control device 34, new network device12 d, or other network devices 12) for the low power network device N 12c and other network devices 12, as represented by arrows 44. Althougharrows 44 are depicted in FIG. 13 as extending to the low power networkdevice N 12 c, the multicast packets of data broadcast from the accesspoint may or may not be sent to the low power network device N 12 c.

The local proxy device 48 may be continually or substantiallycontinuously listening for data packets via a beacon from the accesspoint that are directed at the low power network devices N 12 c forwhich it is acting as a proxy. The local proxy device 48 may identifymulticast packets of data for the low power network devices N 12 c andin response to the local proxy device 48 identifying and receiving aquery request for the low power network device N 12 c via multicastpacket of data, the local proxy device 48 (e.g., as initiated by thecontroller of the local proxy device 48) may respond and broadcast oneor more details of the low power network device N 12 c to the accessport and the network device 12 that sent the query request. Theresponses from the local proxy device 48 may incorporate details of thelow power network device N 12 c (e.g., device name, the services itrenders (e.g., its functionality), its address, and so on), which mayincorporate SRV records, PTR records, TXT records, and/or other records.

The local proxy device 48 may then send any information it receives tothe low power network device N 12 c through a unicast packet of dataand/or by using periodic state information updates. To do this, thelocal proxy device 48 may translate multicast packets of data for thelow power network device N 12 c into unicast packets of data for whichthe low power network device N 12 c may be listening when it is in anawake mode. In some cases, the local proxy device 48 may be configuredto broadcast and/or send the unicast packet of data to the low powernetwork device N 12 c at predetermined intervals. In one example, thelocal proxy device 48 may know when the low power network device N 12 cmay be awake and/or listening for beacons and send the beacons atpredetermined intervals associated with those times.

FIG. 14 illustrates a remote (e.g., server-based and/or wide areaBonjour) sleep/multicast proxy approach. In the remote sleep/multicastproxy approach, a remote proxy device 52 may be utilized. The remoteproxy device 52 may be a computing device (e.g., a server and/or asystem on a server or other device connected to the access point 14 viasecond network (e.g., a WAN, such as the internet)) having a memory, acontroller, an I/O port, and a power source, among other components. Theremote proxy device 52 may be capable of connecting to a first network(e.g., a LAN) on which the network devices 12 may be connected through asecond network (e.g., a WAN) via its I/O port. The remote proxy device52 may be specifically configured to act as a proxy for the low powernetwork device N 12 c, which may be configured to put itself into asleep mode and/or an awake mode to save power during operation. Thepower source of the remote proxy device 52 may be line power or othersource of power. Additionally, the remote proxy device 52 may always orsubstantially always be in an awake mode listening for beacons or othercommunication signals from a first network access point and related toone or more network devices for which it is acting as a proxy.

To setup a low power network device N 12 c with a remote proxy device52, the low power network device N 12 c may register itself with theremote proxy device 52 once it is connected to the first network (e.g.,network 10). To facilitate the registration, the remote proxy device 52may be at a well-known IP address (e.g., an IP address that may beprogramed into network devices 12).

During registration, the low power network device N 12 c may provide itsinternet service provider (ISP) a provided IP address, its local IPaddress on the network, its SRV records, its PTR records, its TXTrecords, its name, the types of services it provides, and/or otherinformation. The remote proxy device 52 may be configured to receivethis information through its I/O port and store the information itsmemory.

The remote proxy device 52 and the low power network devices N 12 c maycommunicate between one another in any manner to allow the low powernetwork device N 12 c to provide the remote proxy device 52 its updateddetails and/or to allow the remote proxy device 52 to provide commands(e.g., from a control device 34) and/or other information to the lowpower network device N 12 c. In one example, the remote proxy device 52may send unicast data packets to the low power network device N 12 c torequest updated information and/or send commands/information.Alternatively, or in addition, the low power network devices N 12 c mayuse periodic state information updates to provide the remote proxydevice 52 with its updated information and/or request information fromthe remote proxy device 52. The periodic state information updates maybe provided without a request from the remote proxy device 52.

In the remote sleep/multicast proxy approach as seen in FIG. 14, the lowpower network device N 12 c may provide its details to the remote proxydevice 52, as represented by arrow 50, and the remote proxy device 52may store the received details in its memory (e.g., cache). Thereafter,an access point may broadcast multicast packets of data (e.g., fromother network devices 12 on the network, such as control device 34, newnetwork device 12 d, or other network devices 12) for the low powernetwork device N 12 c, other network devices 12, and the remote proxydevice 52, as represented by arrows 44. Although arrows 44 are depictedin FIG. 14 as extending to the low power network device N 12 c, themulticast packets of data that are broadcast from the access point andare related to the low power network device N 12 c may or may not besent to the low power network device N 12 c.

The remote proxy device 52 may be continually or substantiallycontinually listening for data packets via a beacon or communicationsignals from the access point that are directed at the low power networkdevices N 12 c for which it is acting as a proxy. In one example, abeacon or communication signal may request address details of alldevices connected to the first network (e.g., LAN), request name detailsof all devices connected to the first network to prevent nameduplication on the first network, request names of services provided byall of the devices on the network, and/or one or more other requests,commands, or information. The remote proxy device 52 may identifymulticast packets of data for the low power network devices N 12 c andin response to the remote proxy device 52 identifying and receiving aquery request for the low power network device N 12 c via multicastpacket of data, the remote proxy device 52 (e.g., as initiated by acontroller of the remote proxy device 52) may respond and broadcast thelow power network device N 12 c information to the access port and thenetwork device 12 that sent the query request. The responses from theremote proxy device 52 may incorporate details of the low power networkdevice N 12 c (e.g., device name, the services it renders (e.g., itsfunctionality), its address, and so forth), which may incorporate SRVrecords, PTR records, TXT records, and/or other records.

The remote proxy device 52 may then send any information it has receivedfrom network devices 12 to the low power network device N 12 c through aunicast packet of data and/or by using periodic state informationupdates. To do this, the remote proxy device 52 may translate multicastpackets of data for the low power network device N 12 c into a unicastpacket of data for which the low power network device N 12 c may belistening when it is in an awake mode. In some cases, the remote proxydevice 52 may be configured to broadcast and/or send the unicast packetof data to the low power network device N 12 c at predeterminedintervals. In one example, the remote proxy device 52 may know when thelow power network device N 12 c may be awake and/or listening forbeacons and send the beacons at predetermined intervals associated withthose times.

A recap may be provided in the following. A computing device may beconfigured to communicate over a network via an access point whilelimiting a total amount of power expended during operation of thecomputing device. The computing device may incorporate an input/output(I/O) interface, a memory, and a controller coupled to the I/O interfaceand the memory. The controller may place the computing device into afirst mode and a second mode. The second mode may allow the controllerto listen via the I/O interface for a beacon from an access point of anetwork to which the computing device is connected. The controller maybroadcast one or more details about the computing device to the accesspoint within a predetermined amount of time after exiting the first modeand without being prompted by a request received from the access point.

The controller of the computing device may broadcast the one or moredetails about the computing device in response to exiting the firstmode. In some cases, the controller of the computing device may beconfigured to automatically broadcast the one or more details about thecomputing device in response to exiting the first mode.

The predetermined amount of time after exiting the first mode at whichthe controller may broadcast one or more details about the computingdevice may be twenty seconds from an immediately prior time the one ormore details about the computing device were broadcast.

The controller of the computing device may broadcast the one or moredetails about the computing device to the access point within thepredetermined amount of time after exiting the first mode and enteringthe second mode.

The computing device may incorporate a power source. In some cases, thepower source may incorporate a battery.

In some cases, during operation of the computing device, less energy maybe used when the computing device is in the first mode than when thecomputing device is in the second mode.

The first mode of the computing device may be a sleep mode.

The sleep mode of the computing device may be a mode in which thecomputing device does not listen for a beacon from the access point.

The one or more details about the computing device may incorporate aplurality of details. In one example, the details may incorporate one ormore of a service record (SRV record), a pointer record (PTR record),and a text record (TXT record).

The one or more details about the computing device may incorporate aplurality of details. In one example, the details may incorporate one ormore of an internet protocol (IP) address and a name for the computingdevice.

The controller of the computing device may broadcast a multicast requestfor information from devices on the network. In some cases, thecontroller may broadcast the multicast request automatically afterexiting the first mode. The controller may respond to the multicastrequest for information by broadcasting the one or more details aboutthe computing device to the access point.

A system for communicating over a local area network via an access pointmay incorporate an access point and a building automation device incommunication with the access point over a local area network. Theaccess point may broadcast multicast packets of data over the local areanetwork to a plurality of devices connected to the local area network.The plurality of devices may incorporate the building automation device.The access point may receive from the plurality of devices a response tothe multicast packets of data that have been broadcast over the localarea network. The building automation device may have a sleep modeduring which the building automation device is not listening forbroadcasts from the access point. The building automation device maybroadcast one or more details about the building automation device tothe access point in response to exiting the sleep mode.

The building automation device may be powered by one or more batteriesfor a period of time during operation of the building automation device.

The building automation device may enter and exit the sleep mode whenthe building automation device is being powered by one or morebatteries.

The building automation device may reduce an amount of power consumedduring operation of the building automation device over a time period.In some the amount of power may be reduced by entering and exiting thesleep mode and automatically broadcasting one or more details about thebuilding automation device to the access point in response to exitingthe sleep mode as compared to an amount of power consumed duringoperation of the building automation device over the time period whenlistening for a broadcast from the access point at a rate at which theaccess point broadcasts multicast packets of data.

The building automation device may broadcast the one or more detailsabout the building automation device to the access point in response toexiting the sleep mode and without being prompted by a request from theaccess point.

The building automation device may listen for broadcasts from the accesspoint when the building automation device is in a mode other than thesleep mode.

An approach of interacting with an access point for a local area networkmay incorporate receiving a beacon at a building automation device. Thebuilding automation device may be connected to the access point over thelocal area network and the beacon is from the access point. The approachmay incorporate sending a response to the received beacon from thebuilding automation device to the access point. The approach may furtherincorporate sending one or more details of the building automationdevice to the access point in response to the building automation deviceexiting the sleep mode and without a prompt from a beacon that isbroadcast by the access point.

In the approach, the building automation device may enter the sleep modeat regular intervals when it is powered by a battery.

In the approach, the building automation device may automatically sendthe one or more details of the building automation device to the accesspoint in response to exiting the sleep mode.

A computing device may communicate over a network via an access pointwhile limiting a total amount of power expended during operation of thecomputing device. The computing device may incorporate an input/output(I/O) interface, a memory, and a controller coupled to the I/O interfaceand the memory. The controller may broadcast via the I/O interface arequest for information from devices connected to the network andreceive via the I/O interface the request for information from devicesconnected to the network. In response to receiving the request forinformation from devices connected to the network, the controller maybroadcast via the I/O interface one or more details about the computingdevice to the access point.

The controller may place the computing device into a first mode and asecond mode. The second mode may allow the controller to listen via theI/O interface for the request for information from devices connected tothe network.

The controller may place the computing device into a first mode and asecond mode. Further, the controller may broadcast via the I/O interfacethe request for information from devices connected to the network inresponse to exiting the first mode.

The controller of the computing device may automatically broadcast therequest for information from devices connected to the network. In somecases, the controller may broadcast the request in response to exitingthe first mode.

The controller of the computing device may broadcast the request forinformation from devices connected to the network. In some cases, thecontroller may broadcast the request within a predetermined amount oftime after exiting the first mode.

The controller of the computing device may broadcast the request forinformation from devices connected to the network. In some cases, thecontroller may broadcast the request within a predetermined amount oftime from an immediately prior request for information from devicesconnected to the network.

The controller of the computing device may broadcast the one or moredetails about the computing device to the access point. In some cases,the controller may broadcast the one or more details within apredetermined amount of time from an immediately prior broadcast of oneor more details about the computing device to the access point.

The computing device may further incorporate a power source. In somecases, the power source may incorporate a battery.

The controller of the computing device may place the computing deviceinto a first mode and a second mode. Less energy may be used by thecomputing device when it is in the first mode than when the computingdevice is in the second mode.

The first mode may be a mode in which the computing device is notlistening for a beacon requesting information from devices connected tothe network.

The one or more details about the computing device may incorporate oneor more of a service record (SRV record), a pointer record (PTR record),and a text record (TXT record).

The one or more details about the computing device may incorporate oneor more of an internet protocol (IP) address and a name for thecomputing device.

A system for communicating over a local area network via an access pointmay incorporate an access point and a building automation device incommunication with the access point over a local area network. Thebuilding automation device may be one of the plurality of devicesconnected to the local area network. Further, the building automationdevice may send to the access point, a multicast packet of dataincluding a request for information from a plurality of devicesconnected to the local area network. The access point may broadcast themulticast packet of data over the local area network to the plurality ofdevices connected to the local area network. In response to receivingthe multicast packet of data broadcast by the access point, the buildingautomation device may broadcast one or more details about the buildingautomation device to the access point.

The building automation device may be powered by one or more batteriesfor a period of time during operation of the building automation device.

The building automation device may enter and exit a sleep mode when thebuilding automation device is being powered by one or more batteries.Further, the building automation device may send to the access point inresponse to exiting the sleep mode the multicast packet of dataincluding the request for information from a plurality of devicesconnected to the local area network.

The building automation device may reduce an amount of power consumedduring operation of the building automation device over a time period byentering and exiting the sleep mode, sending the multicast packet ofdata, and broadcasting one or more details about the building automationdevice to the access point in response to receiving the multicast packetof data as compared to an amount of power consumed during operation ofthe building automation device over the time period when listening for abroadcast from the access point at a rate at which the access pointbroadcasts multicast packets of data.

The building automation device may automatically broadcast the multicastpacket of data. In some cases, the multicast packet of data may beautomatically broadcast in response to exiting a sleep mode.

An approach of interacting with an access point for a local area networkmay incorporate sending from a building automation device to an accesspoint for the local area network a request for information from devicesconnected to the local area network. The building automation device maybe one of the devices connected to the local area network. The approachmay further incorporate receiving at the building automation device fromthe access point the request for information from devices connected tothe local area network. In response to receiving the request forinformation from devices connected to the local area network, theapproach may incorporate sending from the building automation device tothe access point one or more details about the building automationdevice.

In the approach, the building automation device, when powered by abattery, may send the request for information from devices connected tothe local area network at regular intervals.

In the approach, the building automation device may automatically sendthe request for information from devices connected to the local areanetwork in response to exiting a sleep mode.

A computing device may communicate over a network via an access pointwhile limiting a total amount of power expended during operation of oneor more other computing devices connected to the network. A computingdevice may incorporate an input/output (I/O) interface, a memory, and acontroller coupled to the I/O interface and the memory. The controllermay communicate over a network and receive, via the I/O interface andfrom one or more low power devices connected to the network, one or moredetails about the one or more lower power devices. Further, thecontroller may store, in the memory, the received one or more detailsabout the one or more lower power devices and listen for a beacon froman access point of the network.

The controller of the computing device of may broadcast one or moredetails about the one or more low power devices to the access point. Theone or more details may be broadcast by the controller in response tohearing the beacon from the access point.

The controller of the computing device may listen for a beacon from theaccess point. The controller may be listening for a beacon thatincorporates a multicast packet of data for one or more low powerdevices for which the controller stores one or more details.

In response to hearing a beacon from the access point that incorporatesa multicast packet of data for one or more low power devices for whichthe controller stores one or more details, the controller may broadcastone or more details of the one or more low power devices to which themulticast packet of data is to be delivered.

The controller of the computing device may send a unicast query to a lowpower device for which the controller is configured to store one or moredetails. In some cases, the unicast query may request updated detailsfor the low power device.

The controller of the computing device may receive periodic stateupdates from a low power device for which the controller is configuredto store one or more details.

The controller of the computing device may receive periodic stateupdates from a low power device for which the controller is configuredto store one or more details without sending a request to the low powerdevice.

The computing device may incorporate a power source. The power sourcemay be connected to line power.

A system for communicating over a network via an access point mayincorporate a first device connected to the network and in communicationwith an access point for the network, along with a second deviceconnected to the network and in communication with the first device. Thefirst device may store one or more details of the second device and mayreceive multicast packets of data broadcast over the network to aplurality of devices connected to the network. The plurality of devicesincorporates the second device. Further, the first device may identifymulticast packets of data broadcast over the network and directed to thesecond device.

The first device of the system may broadcast one or more stored detailsof the second device to the access point. In some cases, the firstdevice may broadcast the one or more details in response to identifyinga multicast packet of data as being directed to the second device.

The second device of the system may listen for unicast packets of datathat are directed to the second device.

The first device of the system may translate the identified multicastpacket of data into a unicast packet of data. Further, the first devicemay send the unicast packet of data to the second device.

The first device of the system may send a unicast query to the seconddevice. In some cases, the unicast query may request updated detailsfrom the second device.

The first device of the system may repeatedly send the unicast query tothe second device at a predetermined interval.

The first device of the system may receive periodic state updates fromthe second device. The periodic state updates may provide updates to theone or more details stored by the first device.

The first device of the system may receive the periodic state updatesfrom the second device. In some cases, the first device may receive theperiodic state updates without sending a request for an update to thesecond device.

The first device of the system may have a power source configured toconnect to line power. The second device of the system may have abattery as a power source.

The second device of the system may be a thermostat.

An approach of interacting over a network may incorporate listening,with a first device, for a multicast packet of data directed to a seconddevice of which the first device stores one or more details. Themulticast packet of data may be sent by an access point for a network towhich the first device and the second device are connected. The approachmay incorporate identifying with the first device a multicast packet ofdata directed to the second device. The identified multicast packet ofdata may incorporate one or more of a query request for details of thesecond device and a control command for the second device. Further, theapproach may incorporate responding to the identified multicast packetof data with one or more of a detail of the second device and a responseto the control command.

In the approach, the first device may always listen for multicastpackets of data for the second device while connected to the network.

A system for communicating over a network via an access point mayincorporate a low power device connected to a first network and incommunication with an access point for the first network, along with aremote server configured to communicate with the low power device overthe first network via a second network. The remote server may store oneor more details about the low power device and may receive one or moremulticast packets of data broadcast over the first network to aplurality of devices connected to the network. The plurality of devicesmay incorporate the low power device. The remote server may identifymulticast packets of data directed to the low power device.

The remote server of the system may broadcast one or more stored detailsof the low power device over the first network. In some cases, theremote server may broadcast the one or more details in response toidentifying a multicast packet of data as being directed to the lowpower device.

The low power device of the system may listen for unicast packets ofdata that are directed to the low power device.

The remote server of the system may translate the identified multicastpacket of data into a unicast packet of data. Further, the remote servermay send the unicast packet of data to the low power device.

The remote server of the system may send a unicast query to the lowpower device. The unicast query may request updated details from the lowpower device.

The remote server of the system may repeatedly send the unicast query tothe low power device at a predetermined interval.

The low power device of the system may send periodic state updates tothe remote server. The periodic state updates may provide updates to theone or more details stored by the remote server.

The low power device of the system may send periodic state updates tothe remote server. In some cases, the periodic state updates may be sentwithout the low power device receiving a request from the remote serverfor an update to the one or more stored details of the low power device.

The low power device of the system may have a battery as a power source.

The low power device of the system may be a thermostat.

A system for communicating over a network via an access point whilelimiting a total amount of power expended during operation of a lowpower device connected to the network may be noted. The system mayincorporate an access point for a first network and a remote serverconnected to the first network over a second network. The remote servermay store one or more details of a low power device connected to thefirst network. The access point may configured send all multicastpackets of data directed at the low power device to the remote server.The remote server may respond to multicast packets of data directed atthe low power device by sending one or more details of the low powerdevice to the access point.

The remote server of the system may translate received multicast packetsof data directed at the low power device into unicast packets of datafor the low power device.

The system may incorporate a low power device in communication with theaccess point over the first network. The low power device mayperiodically listen for beacons of unicast packets of data directed atthe low power device.

An approach of interacting over a network may incorporate listening,with a remote server, for a multicast packet of data directed to a lowpower device of which the remote server stores one or more details. Themulticast packet of data may be sent by an access point for a firstnetwork and the remote server may be in communication with the accesspoint over a second network. The approach may further incorporateidentifying, with the remote server, a multicast packet of data directedto the low power device. The approach may further incorporateresponding, from the remote server, to the identified multicast packetof data with one or more details of the low power device.

In the approach, the remote server may listen for multicast packets ofdata for the low power device while the low power device is connected tothe first network.

In the approach, the identified multicast packet of data directed to thelow power device may incorporate a query from a control device incommunication with the first network. The query may request addressdetails of all devices connected to the first network. The remote servermay respond to the query with one or more address details of the lowpower device.

In the approach, the identified multicast packet of data directed to thelow power device may incorporate a query from a control device incommunication with the first network. The query may request details ofservices provided by virtually all devices connected to the firstnetwork. The remote server may respond to the query with one or moredetails concerning services provided by the low power device.

In the approach, the low power device may be a thermostat.

In the approach, the identified multicast packet of data directed to thelow power device may incorporate a query from a new device incommunication with the first network. The query may request name detailsof all devices connected to the first network to prevent nameduplication on the first network. The remote server may respond to thequery with a name of the low power device.

The approach may further incorporate receiving, at the remote server, anupdate of one or more details of the low power device. The receivedupdate may be unsolicited by the remote server.

Any publication or patent document noted herein is hereby incorporatedby reference to the same extent as if each publication or patentdocument was specifically and individually indicated to be incorporatedby reference.

In the present specification, some of the matter may be of ahypothetical or prophetic nature although stated in another manner ortense.

Although the present system and/or approach has been described withrespect to at least one illustrative example, many variations andmodifications will become apparent to those skilled in the art uponreading the specification. It is therefore the intention that theappended claims be interpreted as broadly as possible in view of therelated art to incorporate all such variations and modifications.

What is claimed is:
 1. A system for communicating over a network via anaccess point, the system comprising: a first device connected to anetwork and in communication with an access point for the network; and asecond device connected to the network and in communication with thefirst device, wherein the second device is a building automation device,wherein a building automation device comprises one or more of: a camera,a carbon monoxide detector, a smoke detector, a light bulb, a buildingautomation sensor and a heating, air conditioning and ventilation (HVAC)controller device, and wherein the second device is configured toautomatically enter and exit a power saving state and, while in thepower saving state, not communicate with the first device or the accesspoint; and wherein: the first device is configured to: store one or moredetails of the second device, receive periodic state updates from thesecond device without sending a request for an update to the seconddevice, update the one or more details based on the periodic updates,receive multicast packets of data on the network to a plurality ofdevices connected to the network, wherein the plurality of devicescomprises the second device, and identify multicast packets of data onthe network that are directed to the second device.
 2. The system ofclaim 1, wherein the first device is configured to broadcast one or morestored details of the second device to the access point in response toidentifying a multicast packet of data as being directed to the seconddevice.
 3. The system of claim 1, wherein: the second device isconfigured to listen for unicast packets of data that are directed tothe second device; and the first device is configured to translate theidentified multicast packet of data into a unicast packet of data andsend the unicast packet of data to the second device.
 4. The system ofclaim 1, wherein: the second device is configured to listen for unicastpackets of data that are directed to the second device; the first deviceis configured to send a unicast query to the second device, wherein theunicast query is configured to request updated details from the seconddevice; and the first device is configured to repeatedly send theunicast query to the second device at a predetermined interval.
 5. Thesystem of claim 1, wherein: the first device has a power sourceconfigured to connect to line power and the second device has a batteryas a power source.
 6. A method of interacting over a network, the methodcomprising: listening, with a first device, for a multicast packet ofdata directed to a second device wherein the second device is a buildingautomation device, wherein a building automation device comprises one ormore of: a camera, a carbon monoxide detector, a smoke detector, a lightbulb, a building automation sensor and a heating, air conditioning andventilation (HVAC) controller device, and wherein the multicast packetof data is sent by an access point for a network to which the firstdevice and the second device are connected; storing, by the firstdevice, one or more details of the second device; automatically enteringand exiting, by the second device, a power saving state, wherein whilein the power saving state the second device does not communicate withthe first device or the access point; identifying with the first devicethe multicast packet of data directed to the second device, wherein theidentified multicast packet of data incorporates one or more of a queryrequest for the details of the second device and a control command forthe second device; and responding to the identified multicast packet ofdata with one or more of the details of the second device and a responseto the control command.
 7. The method of claim 6, wherein the firstdevice is configured to always listen for multicast packets of data forthe second device while connected to the network.
 8. The method of claim6, wherein the second device is configured to listen for unicast packetsof data that are directed to the second device, the method furthercomprising, translating, by the first device the identified multicastpacket of data directed to the second device into a unicast packet ofdata; and sending, by the first device, the unicast packet of data tothe second device.
 9. The method of claim 8, further comprising,sending, by the first device, a unicast query to the second device,wherein the unicast query is configured to request updated details fromthe second device; and the first device is configured to repeatedly sendthe unicast query to the second device at a predetermined interval. 10.The method of claim 6, wherein the first device has a power sourceconfigured to connect to line power and the second device has a batteryas a power source.